<html>
<head>
<title> Setting Up Spam Protection </title>
<meta name="Keywords" content="" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="stylesheet" type="text/css" href="stylesheet.css"/>
<script src="locate.js"></script>
<link href="prettify.css" type="text/css" rel="stylesheet" />
<script type="text/javascript" src="prettify.js"></script>
</head>
<script src="highlight.js"></script>
<body bgcolor="#FFFFFF" text="#000000" link="#0000A0" alink="#008000" vlink="#FF0000" onLoad="FindCorrectTOCPage(); prettyPrint()">
<table cellpadding="0" cellspacing="0" border="0">
<tr valign="top">
<td>
<p class="pagenavigation"><a href="16767.htm" target="_self"><img src="38976.gif" alt="Previous page" height="16" width="16" vspace="0" hspace="1" align="top" border="0"> Previous page</a></p></td>
<td>
<p class="pagenavigation"><a href="16875.htm" target="_self"><img src="38977.gif" alt="Next page" height="16" width="16" vspace="0" hspace="1" align="top" border="0"> Next page</a></p></td>
<td>
<p class="pagenavigation"><a href="toc4151860.htm" target="TOC"><img src="38970.gif" alt="Locate page" height="16" width="16" vspace="0" hspace="1" align="top" border="0"> Locate page</a></p></td>
<td>
<p class="pagenavigation"><a href="toc4151860.htm" target="TOC"><a class="" title="" href="javascript:print();" target="_self"><img src="39072.gif" alt="Print this page" height="16" width="16" vspace="0" hspace="1" align="top" border="0"></a></a></p></td>
</tr>
</table>
<h3 class="heading3">Setting Up Spam Protection</h3>
<p class="bodytext">To protect your users from spam, you can use the following tools with your control panel:</p>
<ul class="listbullet"><li class="listbullet"><strong class="specialbold">SpamAssassin spam filter</strong>. It is a powerful spam filter that uses a wide variety of local and network tests to identify spam signatures.<p class="listcontinue">You can configure the spam filter so as to either delete suspicious messages when they come to your mail server, or change the subject line and add &quot;X-Spam-Flag: YES&quot; and &quot;X-Spam-Status: Yes&quot; headers to the messages. The latter can be useful for users who prefer to filter mail with mail filtering programs installed on their own computers.</p>
<p class="listcontinue">To learn more about SpamAssassin, visit <a class="externalhyperlinktemplate" title="" href="http://spamassassin.apache.org" target="_blank">http://spamassassin.apache.org</a>.</p>
<p class="listcontinue">To configure and switch on the SpamAssassin filter, proceed to the <a id="h17734" class="jumptemplate" title="Setting Up SpamAssassin Spam Filter" href="16875.htm" target="_self">Setting Up SpamAssassin Spam Filter</a> section.</p>
</li><li class="listbullet"><strong class="specialbold">DomainKeys</strong>. DomainKeys is a spam protection system based on sender authentication. When an e-mail claims to originate from a certain domain, DomainKeys provides a mechanism by which the recipient system can credibly determine that the e-mail did in fact originate from a person or system authorized to send e-mail for that domain. If the sender verification fails, the recipient system discards such e-mail messages. To configure the DomainKeys system on your server, refer to the section <a id="h57143" class="jumptemplate" title="Setting Up Spam Protection Based on DomainKeys" href="56325.htm" target="_self">Switching on Spam Protection Based on DomainKeys</a>.</li><li class="listbullet"><strong class="specialbold">DNS blackhole lists</strong>. This spam prevention system is based on DNS queries made by your mail server to a database, which contains known and documented sources of spam, as well as an extensive listing of dynamic IP addresses. Any positive response from this database should result in your mail server returning a '550' error, or rejection of the requested connection.<p class="listcontinue">To configure your mail server for working with DNSBL databases, proceed to the <a id="h43548" class="jumptemplate" title="Switching On Spam Protection Based on DNS Blackhole Lists" href="16876.htm" target="_self">Switching On Spam Protection Based on DNS Blackhole Lists</a> section.</p>
</li><li class="listbullet"><strong class="specialbold">Sender Policy Framework (SPF)</strong>. This spam prevention system is also DNS query-based. It is designed to reduce the amount of spam sent from forged e-mail addresses. With SPF, an Internet domain owner can specify the addresses of machines that are authorized to send e-mail for users of his or her domain. Receivers that implement SPF then treat as suspect any e-mail that claims to come from that domain but fails to come from locations that domain authorizes.<p class="listcontinue">To learn more about SPF, visit <a class="externalhyperlinktemplate" title="" href="http://www.openspf.org/howworks.html" target="_blank">http://www.openspf.org/howworks.html</a>.</p>
<p class="listcontinue">To enable filtering based on SPF, proceed to the <a id="h17736" class="jumptemplate" title="Setting Up Support for Sender Policy Framework System" href="16877.htm" target="_self">Setting Up Support for Sender Policy Framework System</a> section.</p>
</li><li class="listbullet"><strong class="specialbold">Server-wide black and white lists</strong>. Black and white lists are standard mail server facilities. You can use the black list to specify the domains from which mail must not be accepted, and white list to specify the IP addresses of machines or networks from which mail must always be accepted.<p class="listcontinue">To set up server-wide black and white lists, proceed to the <a id="h17737" class="jumptemplate" title="Setting Up Server-wide Black and White Lists" href="17168.htm" target="_self">Setting Up Server-wide Black and White Lists</a> section.</p>
</li></ul><table cellpadding="0" cellspacing="0" border="0">
<tr valign="top">
<td>
<p class="relatedheading">In this section:</p><p class="relateditem"><a href="16875.htm" target="_self">Setting Up SpamAssassin Spam Filter</a></p><p class="relateditem"><a href="56325.htm" target="_self">Setting Up Spam Protection Based on DomainKeys</a></p><p class="relateditem"><a href="16876.htm" target="_self">Switching On Spam Protection Based on DNS Blackhole Lists</a></p><p class="relateditem"><a href="16877.htm" target="_self">Setting Up Support for Sender Policy Framework System</a></p><p class="relateditem"><a href="17168.htm" target="_self">Setting Up Server-wide Black and White Lists</a></p></td>
</tr>
</table>



</body>
<script>highlightTOC()</script>
</html>

